Exclude Services tests from Linux JS Tests
Job and Separate Workflow for flaky Selenium Tests
#105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update: 06/03/22
Originally, this PR attempted to pin jupyter_client <7.x to fix the services (macOS)
Linux JS Tests
job.However, while pinning jupyter_client <7.x allows the macOS services tests consistently pass locally, the CI test results are not consistent. That change has been discarded.
Currently, the services (Ubuntu and macOS) tests are being excluded and are to be further addressed in a separate issue.
Lastly, creating a separate workflow for flaky selenium tests
Using jupyter_client 7.x dependency leads to different behavior.
The execution of the following code in a cell, results in only two of the four expected events
The two events trigged: 'kernel_restarting.Kernel', 'kernel_autorestarting.Kernel'
The two events not triggered: 'kernel_killed.Session', 'kernel_dead.Kernel'